FAQs

Where are Visibility skill logs located?

Debug logs: /var/log/efa/evm/evm-server.log

Error logs (with panic trace): /var/log/efa/evm/evm-server_err.log

Where are the Inventory Service logs located?

Debug logs: /var/log/efa/inventory/inventory-server.log

Error logs (with panic trace): /var/log/efa/inventory/inventory-server_err.log

Where are the Installer logs located?

/var/log/efa/installer/<installer_.....log>

All installation failures are reported in this log.

What are some common reasons for installation failures?

  • The operating system version is incorrect.
  • The amount of available hard disk space is insufficient. At least 50 GB should be available.
  • In a multi-node installation, the operating system and clock do not match. Or, both nodes have the same host name.

Why does the web user interface not load on the browser?

The most probable reason is that TCP port 443 is blocked through a firewall. Unblocking this port should enable the UI to be loaded.

What are some common reasons for XCO log-in failures?

  • The user credentials are entered incorrectly.
  • TACACS+ or LDAP is not reachable or not configured correctly for the xco-role.
  • The xco-role in TACACS+ or LDAP is not mapped to a predefined role such as NetworkOperator or SystemAdmin.

Where are authentication failures captured?

Debug logs: /var/log/efa/auth/auth-server.log

Error logs (with panic trace): /var/log/efa/auth/auth-server_err.log

What are possible reasons for device registration failures?

  • The device is not reachable from ExtremeCloud Orchestrator.
  • The device credentials are incorrect.
  • The HTTPS, SSH, NETCONF, or GNMI ports are blocked.
  • The device versions are not supported.
  • The device has exceeded the maximum limit on SSH connections. Free up some existing connections that are used by other tools and try to register again.

Why is there a delay in loading the dashboard or statistics in the web UI?

It can take from 20 seconds to 1 minute to load live statistics from a device.

Why is the device configuration blocked from the web UI?

The device can have missed a heartbeat and subsequently transitioned to a degraded state. The device should be accessible when connectivity is restored.

What are possible reasons for configuration failures?

  • The XCO user does not have permission to make changes to the device.
  • The web UI reports validation errors or errors received from the device.
  • The credentials used for device registration do not have permission to make changes to the device.

How do I check that all services are up and running?

Run the following command on the XCO device: 
k3s kubectl get pods -n efa
The following is sample output.
NAME                           READY   STATUS    RESTARTS   AGE
efa-api-docs-84cwl             1/1     Running   0          20d
ui-service-54dbbb47fd-vzfrw    1/1     Running   0          20d
gosystem-service-dw4vj         1/1     Running   0          20d
rabbitmq-4tgsv                 1/1     Running   0          20d
gorbac-service-j6lp8           1/1     Running   0          20d
goevm-service-sjckq            1/1     Running   0          20d
gonotification-service-grvx9   1/1     Running   0          20d
gofaultmanager-service-nstwf   1/1     Running   0          20d
goauth-service-qffvs           1/1     Running   0          20d
goraslog-service-s7mwt         1/1     Running   0          20d
goinventory-service-q5sdl      1/1     Running   0          20d

Why are the device syslogs not visible?

Other tools that are registered with the device could have exceeded the maximum limit for syslogs. Free up any stale syslog entries on the device and then re-register the device.

How to collect the SupportSave data for troubleshooting?

Run the following command on the XCO device: 
efa system supportsave
The following is a sample output.
SupportSave File Location: /var/log/efa/efa_2022-11-17T18-40-41.008.logs.zip
--- Time Elaspsed: 21.584259642s ---

To collect the SupportSave data using the XCO GUI, see Support Save.

9038969-00 Rev AA